home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
doors_1
/
lockdoor.zip
/
LOCKDOOR.DOC
< prev
next >
Wrap
Text File
|
1992-10-02
|
10KB
|
283 lines
╓───────────────────────────────────────────────────────────╖
║ ║
║ LockDoor ║
║ (A PCBoard 14.5 Utility) ║
║ ║
║ LockDoor Version 1.3 ║
║ ║
║ Copyright (C) 1992 by David D. Casto ║
║ ALL RIGHTS RESERVED ║
║ ║
║ 6196 Deewood Loop East ║
║ Columbus, Ohio 43229 ║
║ (614) 882-0994 ║
║ ║
╙───────────────────────────────────────────────────────────╜
LockDoor Version 1.3 - LockDoor.DOC - USER MANUAL Page - II
-----------------------------------------------------------------------------
Table Of Contents:
=================
Cover Page .......................................... I
Table Of Contents ................................... II
Legal Information ................................... 1
Registration ........................................ 1
Program Description ................................. 2
How LockDoor Works .................................. 2
Set Up .............................................. 2
Example Door Batch Files ............................ 3
Example Display File ................................ 4
Comments ............................................ 4
What's New .......................................... 5
LockDoor Version 1.3 - LockDoor.DOC - USER MANUAL Page - 1
-----------------------------------------------------------------------------
LockDoor Version 1.3
Copyright (C) 1992 by David D. Casto
ALL RIGHTS RESERVED
6196 Deewood Loop East
Columbus, Ohio 43229
(614) 882-0994
WARNING!!
-------
As with all new software it is *STRONGLY* recommended that you have a
recent backup just in case.
Legal:
-----
David Casto hereby disclaims all warranties relating to this
software, whether express or implied, including without limitation any
implied warranties of merchantability or fitness for a particular
purpose. David Casto will not be liable for any special, incidental,
consequential, indirect or similar damages due to loss of data or any
other reason, even if David Casto or an agent of David Casto has been
advised of the possibility of such damages. In no event shall David
Casto liability for any damages ever exceed the price paid for the
license to use software, regardless of the form of the claim. The
person using the software bears all risk as to the quality and
performance of the software.
You are free to distribute this software as long as there are no
modifications to any files in this Archive.
Registration:
LockDoor is a free utility to all registered PCBEvent users. LockDoor
will not work unless you have a registered PCBEvent key!
LockDoor Version 1.3 - LockDoor.DOC - USER MANUAL Page - 2
-----------------------------------------------------------------------------
What Is LockDoor? :
=================
LockDoor is a utility that will lock a door xx minuets before an event
preventing event over run.
How LockDoor Works:
==================
LockDoor reads PCBEvent.cfg to determine the path to the node's home
directory. LockDoor then reads PCBoard.dat and calculates the time
remaining until your next event. If the time remaining is equal to or
less than the xx minuets that was specified on the command line, an
errorlevel of 10 will be returned to DOS. The errorlevel is then checked
by your door batch file. In the example door batch file below, if the
errorlevel is 10 then it will go to the LOCK label, copy DoorLock.txt to
PCBDoor.txt and reload the board. PCBoard will then display DoorLock.txt
to the user. If the time remaining is greater than the time specified on
the command line an errorlevel of 0 is returned to DOS therefore by-
passing the LOCK and opening the door.
Setup:
=====
1.) Place LockDoor.exe in your PCBEvent directory. Make LockDoor.exe read
only (See ReadOnly.doc). You should have the SET PCBEvent environment
variable installed in your environment and the PCBEvent directory
should be in your DOS path. If you have set up PCBEvent with the SET
PCBEvent environment variable, and have the PCBEvent directory in your
DOS path you can run LockDoor from any directory. If you do not have
PCBEvent set up with the DOS environment variable and the PCBEvent
directory is not in your DOS path, you will need to execute LockDoor
from the PCBEvent directory.
2.) Edit each door batch file that you want to use LockDoor on. (see
batch file examples).
3.) Place and edit a LockDoor.txt (or any Path\FileName) in a directory
(see example).
4.) Please let me know if you like LockDoor!
LockDoor Version 1.3 - LockDoor.DOC - USER MANUAL Page - 3
-----------------------------------------------------------------------------
Example Door Batch Files For Node 1:
===================================
--------------------------
Regular Door Batch File:
--------------------------
@ECHO OFF
LockDoor 1:45:Y
IF ERRORLEVEL == 10 GOTO LOCK
CD\MYDOOR
MYDOOR
GOTO END
:LOCK
COPY C:\PCB\GEN\LockDoor.txt C:\PCB\PCBDOOR.txt>NUL
:END
C:
CD\PCB
BOARD
------------------------
Shell Door Batch File:
------------------------
@ECHO OFF
LockDoor 1:45:Y
IF ERRORLEVEL == 10 GOTO LOCK
CD\MYDOOR
MYDOOR
GOTO END
:LOCK
COPY C:\PCB\GEN\LockDoor.txt C:\PCB\PCBDOOR.txt>NUL
:END
C:
CD\PCB
EXIT
LockDoor Version 1.3 - LockDoor.DOC - USER MANUAL Page - 4
-----------------------------------------------------------------------------
Example LockDoor.txt:
==================
@CLS@@BEEP@@BEEP@@BEEP@
@X0C────────────────────────────────────────────────────────────────────────────
@X8CPLEASE NOTE
@X0FThis door has been @X0CLOCKED @X0Fdue to a scheduled event.
Please try this door again after our event at @EVENT@.
Thank You
Your SysOp
@X0C────────────────────────────────────────────────────────────────────────────
@WAIT@
Comments:
========
LockDoor was constructed due to several doors that do not check the
next event time. This can result in a user being in a door and therefor
over running an event.
If you have any problems installing LockDoor or any of my doors or
utilities feel free to call me voice at 614-882-0994. I monitor the DOOR
and UTILITY conferences on Salt Air. I also monitor the Rime PCBHints
conference.
* Note: Please address all correspondence to David Casto.
*****************************************************************
Blue Light BBS is located in Columbus, Ohio
Support Conference #99
(614) 766-9708 14400 BPS
(614) 766-9709 19200 BPS
LockDoor Version 1.3 - LockDoor.DOC - USER MANUAL Page - 5
-----------------------------------------------------------------------------
What's NEW:
==========
Version 1.0
-----------
Initial release.
Version 1.1
-----------
Added - Will now read the PCBEvent.cfg and the environment to get the
needed information without Door.sys.
Added - There are now three command line parameters. The syntax is
"LockDoor NodeNumber:Min:OverRide". The NodeNumber is the Node Number
that is running LockDoor. NodeNumber may be a DOS SET variable. Min is
the Minuets before the event to disable the door. OverRide is a "Y" or
"N" (Y for yes and N for no). OverRide will over ride the event checking
if the next event is set to Slide if user is on-line. Default OverRide is
NO and is not required on the command line.
Added - Several other small cosmetic changes.
Version 1.3
-----------
Added - Ability to read the new PCBEvent key files.
Added - Ability to read the New PCBEvent environment variables.
Removed - High Color screen displays.